The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

lib/zip/uncompress_stream.js (2)

42-48: _finalCallback overwritten later – can lose debug/error emit wrapper.
When _final runs it replaces _finalCallback with the raw callback, so subsequent errors (e.g. openReadStream failure) skip the debug log and emit path defined here.
Wrap the stream’s callback instead of wholesale replacing the property to keep consistent logging/emission behaviour.

---

74-80: Possible back-pressure / type-safety issue in _write.
• callback() is invoked immediately after buffering; large archives will still accumulate unbounded RAM, but at least honour stream.Writable back-pressure by waiting for high-water-mark drain signals (defer callback until this.push equivalent).
• debug('write size: %d', chunk.length) assumes chunk is a Buffer; if a string is written the %d formatter will coerce incorrectly.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

.github/workflows/release.yml (1)

9-13: Add back the NPM_TOKEN secret so npm publish can authenticate

Without explicitly passing NPM_TOKEN into the reusable workflow, semantic-release will not have the credentials needed to publish to npm and will fail.

Please update .github/workflows/release.yml to include:

 jobs:
   release:
     name: NPM
     uses: node-modules/github-actions/.github/workflows/npm-release.yml@master
     secrets:
       GIT_TOKEN: ${{ secrets.GIT_TOKEN }}
+      NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/nodejs.yml (1)

3-11: Optional: add concurrency to reduce duplicate CI runs across push/pull_request/merge_group.

Helps cancel superseded runs on the same ref.

Apply:

 name: CI

 on:
   push:
     branches: [ master ]

   pull_request:
     branches: [ master ]

   merge_group:

+concurrency:
+  group: ci-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

test/zip/index.test.js (1)

29-29: Prefer removing commented-out code or using a toggleable debug helper

Leaving commented-out logs around causes drift. Either remove them entirely or switch to a conditional debug helper so you can enable logs locally without code changes.

Option A — remove the dead lines:

-      // console.log('dest', destFile);
-      // console.log('dest', destFile);
-      // console.log('dest', destFile);
-      // console.log('dest', destFile);
-      // console.log('dest', destFile);
-      // console.log('dest', destFile);
-      // console.log('dest', destFile);
-      // console.log('dest', destFile);
-    // console.log('dest', destFile);
-    // console.log(destDir);

Option B — keep them but behind a debug helper:

-      // console.log('dest', destFile);
+      debug('dest', destFile);
-      // console.log('dest', destFile);
+      debug('dest', destFile);
-      // console.log('dest', destFile);
+      debug('dest', destFile);
-      // console.log('dest', destFile);
+      debug('dest', destFile);
-      // console.log('dest', destFile);
+      debug('dest', destFile);
-      // console.log('dest', destFile);
+      debug('dest', destFile);
-      // console.log('dest', destFile);
+      debug('dest', destFile);
-      // console.log('dest', destFile);
+      debug('dest', destFile);
-    // console.log('dest', destFile);
+    debug('dest', destFile);
-    // console.log(destDir);
+    debug(destDir);

Add this small helper near the top of the file (or import from a shared test util):

// test/util/debug.js (recommended) or inline in this file
const DEBUG = process.env.TEST_DEBUG === '1';
function debug(...args) {
  if (DEBUG) console.log(...args);
}

Also applies to: 40-40, 73-73, 85-85, 98-98, 109-109, 120-120, 130-130, 282-282, 293-293

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro